home *** CD-ROM | disk | FTP | other *** search
- Path: news01.aud.alcatel.com!usenet
- From: lewikk@grasshopper.aud.alcatel.com (Kevin K. Lewis)
- Newsgroups: comp.object,comp.lang.sather,comp.lang.eiffel,comp.lang.c++
- Subject: UNIX Process Management
- Date: 17 Apr 1996 14:00:52 -0500
- Organization: Alcatel Network Systems
- Sender: lewikk@grasshopper.aud.alcatel.com
- Message-ID: <qcw91fullp7.fsf@grasshopper.aud.alcatel.com>
- NNTP-Posting-Host: grasshopper.aud.alcatel.com
- X-Newsreader: Gnus v5.1
-
-
- Does anyone know of significant work done on managing UNIX
- processes/tasks as objects? I'm looking for something that describes
- processes as objects, including how one:
-
- o Creates and destroys a task (fork+exec, kill)
-
- o Communicates with a task:
-
- o through a consistent and flexible interface (something
- like task.send(message), where message is an abstract base class
- of all message classes, as in the following bullet).
-
- o using sockets, streams, signals and mail (msgsnd,msgrcv)
-
- o that already exists
-
- o Establishes a client-server relationship with a new or existing
- task
-
- I've thought about this a bit, but I'm not sure if I'm going in the
- right direction. I've looked at offerings from some vendors, but they
- don't seem to provide the full picture (they mostly concentrate on
- communication, which is good but not enough).
-
- I can use either code (I'd prefer Sather, Eiffel, or C++, since I read
- those best), class and object diagrams (I can read BON, Fusion, Booch
- and OMT), or a reference to a published work (article, book, etc).
-
- Thanks for any help or insight.
- --
- Kevin K. Lewis | My opinions may be unreasonable
- lewikk@aud.alcatel.com | but such is the voice of inspiration
-